Logistics APIs
Details for provided shipping service
HTTP method | GET |
URI | https://api.rambase.net/logistics/shipping-services/{shippingServiceId} |
Supported formats | Xml, Html, Json (ex. $format=json) |
- URI parameter {shippingServiceId} |
Shipping service identifier
Integer, minimum 100000 |
Successful HTTP status code | 200 |
API resource identifier | 2092, version 18 |
The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.
The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.
$showDomainDescriptions Boolean, optional | Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false. |
$lang String, optional | Specifies the language used in the response, following the 3-letter ISO-639-1 [lll] |
$access_token String, optional | After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time. |
$db String, optional | Set the database/company for the request |
$format String, optional | Set the format of the response to use for the request. Accepted values are "xml", "html", "jsonstream", "json" |
$useMinimumVersion Integer, optional | Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information. |
$select String, optional | Use to define the fields to return in the response. Accepts a comma-separated list of field names. See the Expand and select page for more information. |
$expand String, optional | Use to include output fields that are not returned by default in the response. Accepts a comma-separated list of expandable field names. See the Expand and Select page for more information. |
Read more about filters and sorting on how to use filter parameters and named filters.
Read more about filters and sorting on how to use sortable parameters
Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.
Please note that some fields may be removed from the response, based on user roles/duties/permissions.
ShippingServiceId
Shipping service identifier
>{Integer}</ShippingServiceId>Name
Name of shipping service
>{String}</Name>CreatedAt
Date and time of creation
>{Datetime}</CreatedAt>Description
Description of shipping service
>{String}</Description>Direction
Direction of goods for this shipping service. Is goods arriving by this shipping service (INCOMING), or is departing (OUTGOING).
Possible domain values can be found here
>{String}</Direction>IsAvailableExternal
True if shipping service should be visibile in external systems. An example of an external system might be a web site.
>{Boolean}</IsAvailableExternal>DepartingWaybillConsolidationTag
All shipping services with same consolidation tag will be consolidated when creating departing waybills for shipping advices, supplier returns and goods transfers. Example of consolidation tag might be "UPSNORDIC".
>{String}</DepartingWaybillConsolidationTag>PayersCustomerIdAtCarrier
Customers account ID at the carrier for the given shippingservice
>{String}</PayersCustomerIdAtCarrier>CarrierId
Carrier identifier
>{Integer}</CarrierId>CarrierLink
Carrier reference
>{String}</CarrierLink>CarrierServiceId
Shipping service identifier from arhive for shipping services
>{Integer}</CarrierServiceId>CarrierServiceLink
Service reference
>{String}</CarrierServiceLink>ExclusivelyForCustomer
Some shipping services are exclusively for one customer only.
>CustomerId
Customer identifier
>{Integer}</CustomerId>CustomerLink
Customer reference
>{String}</CustomerLink>ReturnShippingService
The shipping service that should be used when shipments that are shipped with this shipping service are returned. For instance you might not have to use an expensive express delivery for the return of products.
>ShippingServiceId
Shipping service identifier
>{Integer}</ShippingServiceId>Name
Name of shipping service
>{String}</Name>ReturnShppingServiceLink
Shipping service reference
>{String}</ReturnShppingServiceLink>ShippingServiceId
Shipping service identifier
": "{Integer}",Status
Status of shipping service
Possible domain values can be found here
": "{Integer}",Name
Name of shipping service
": "{String}",CreatedAt
Date and time of creation
": "{Datetime}",Description
Description of shipping service
": "{String}",Direction
Direction of goods for this shipping service. Is goods arriving by this shipping service (INCOMING), or is departing (OUTGOING).
Possible domain values can be found here
": "{String}",IsAvailableExternal
True if shipping service should be visibile in external systems. An example of an external system might be a web site.
": "{Boolean}",DepartingWaybillConsolidationTag
All shipping services with same consolidation tag will be consolidated when creating departing waybills for shipping advices, supplier returns and goods transfers. Example of consolidation tag might be "UPSNORDIC".
": "{String}",PayersCustomerIdAtCarrier
Customers account ID at the carrier for the given shippingservice
": "{String}",CarrierId
Carrier identifier
": "{Integer}",CarrierLink
Carrier reference
": "{String}"CarrierServiceId
Shipping service identifier from arhive for shipping services
": "{Integer}",CarrierServiceLink
Service reference
": "{String}"ExclusivelyForCustomer
Some shipping services are exclusively for one customer only.
": {CustomerId
Customer identifier
": "{Integer}",CustomerLink
Customer reference
": "{String}"ReturnShippingService
The shipping service that should be used when shipments that are shipped with this shipping service are returned. For instance you might not have to use an expensive express delivery for the return of products.
": {ShippingServiceId
Shipping service identifier
": "{Integer}",Name
Name of shipping service
": "{String}",ReturnShppingServiceLink
Shipping service reference
": "{String}"
List of available operations/actions for this resource.
See the operations documentation for more information about API operations.
Possible error codes the response might return:
Error 102738 HTTP 404 | Price list not found |
Error 100055 HTTP 403 | You have only admittance to your own objects |